-
Notifications
You must be signed in to change notification settings - Fork 3.1k
[exporter/azuremonitor] enchancement AND semantic update to 1.34.0 #43703
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[exporter/azuremonitor] enchancement AND semantic update to 1.34.0 #43703
Conversation
|
Welcome, contributor! Thank you for your contribution to opentelemetry-collector-contrib. Important reminders:
A maintainer will review your pull request soon. Thank you for helping make OpenTelemetry better! |
b335149 to
b653cc0
Compare
b653cc0 to
fe9a08f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code changes LGTM - let's see if CI is green.
|
Thank you for your contribution @kyle-mccray! 🎉 We would like to hear from you about your experience contributing to OpenTelemetry by taking a few minutes to fill out this survey. If you are getting started contributing, you can also join the CNCF Slack channel #opentelemetry-new-contributors to ask for guidance and get help. |
Description
From issue the AspNet OTEL instrumentation was upgraded to use semantic version 1.24.0. This became a breaking change for the azure monitor exporter that was stuck on 1.12.0/1.27.0/1.7.0 semantic versions. This PR updates the azure monitor exporter to 1.34.0
Link to tracking issue
Fixes #41289
Testing